Skip to content

Conversation

@Earlopain
Copy link
Collaborator

Currently I find them hard to follow because there are just so many methods.

This groups them by topic instead so that the more unique methods appear first. I also added call-seqs because we have the type information, so why not.

Currently there are two bugs with sections in rdoc (ruby/rdoc#1603, ruby/rdoc#1600), screenshots are with them fixed.

Before:

Prism::Node
Prism::CallNode

After:

Prism::Node
Prism::CallNode

@Earlopain Earlopain force-pushed the better-node-docs branch 2 times, most recently from a32d28e to a78e447 Compare February 8, 2026 17:00
Currently I find them hard to follow because there are just so many methods.

This groups them by topic instead so that the more unique methods appear first.
I also added call-seqs because we have the type information, so why not.
@kddnewton kddnewton merged commit caf018e into ruby:main Feb 9, 2026
67 checks passed
matzbot pushed a commit to ruby/ruby that referenced this pull request Feb 9, 2026
(ruby/prism#3912)

Currently I find them hard to follow because there are just so many methods.

This groups them by topic instead so that the more unique methods appear first.
I also added call-seqs because we have the type information, so why not.

ruby/prism@caf018ec50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants